Variable dose dispensing system

ABSTRACT

A variable dose dispensing system may include a processor and memory. The processor may receive a request for a variable dose order of a medication, such as from a user. The processor may request an amount of the medication to be administered, and receive, in response to the request, an indication of the amount to be administered. The processor may verify that the amount to be administered is within a range of the variable dose order. The processor may determine an item in a local inventory that contains at least the amount of the medication to be administered, and may dispense the item. If an amount of the dispensed item exceeds the amount to be administered, such as by a waste amount, the processor may display an indication of the waste amount to the user, and may transmit a notification of the waste amount, such as to a management server.

CROSS-REFERENCE TO RELATED APPLICATIONS

The presented application is a continuation of U.S. patent applicationSer. No. 15/804,100 entitled “VARIABLE DOSE DISPENSING SYSTEM,” filed onNov. 6, 2017, which is a divisional of U.S. patent application Ser. No.15/134,962 entitled “VARIABLE DOSE DISPENSING SYSTEM,” filed on Apr. 21,2016, now U.S. Pat. No. 9,842,196, issued Dec. 12, 2017, which is adivisional of U.S. patent application Ser. No. 13/754,724 entitled“VARIABLE DOSE DISPENSING SYSTEM,” filed on Jan. 30, 2013, now U.S. Pat.No. 9,342,484, issued May 17, 2016, the disclosures of which are herebyincorporated by reference in their entirety for all purposes.

TECHNICAL FIELD

The present description relates generally to dispensing, and moreparticularly, but not exclusively, to variable dose dispensing.

BACKGROUND

Healthcare facilities, such as hospitals, may utilize medicationdispensing devices, such as automated dispensing machines (ADMs), toprovide healthcare professionals with controlled access to medications.For example, a medication dispensing device may be stocked, e.g by apharmacy, with multiple medications that may each have a variety ofdifferent doses and a variety of different forms, e.g. tablet, caplet,etc. A pharmacy will communicate an order for an amount of a medicationprescribed for a patient, e.g. 2 milligrams (mg) of morphine, to amedication dispensing device, such as over a network. A healthcareprofessional, such as a nurse, will authenticate with the medicationdispensing device and select the order. The medication dispensing devicethen physically dispenses the ordered amount of the medication to thehealthcare professional. The healthcare professional then administersthe dispensed medication to the patient. In some examples, themedication dispensing device may be configured to only dispense to thehealthcare professional, and/or to only provide the healthcareprofessional with physical access to, the amount of the medication thatwas prescribed. In this manner, the amount of wasted medication issubstantially minimized and the healthcare facility can control thehealthcare professional's access to the medication.

However, in some instances an order received from a pharmacy may be fora variable dose of a medication, e.g. a range of 2-10 mg of morphine. Inthis instance, the medication dispensing device may allow the healthcareprofessional to select the medication item(s) that they would like toaccess, and the medication dispensing device may grant the healthcareprofessional with access to the selected medication item(s) so long asthe total amount of the medication being dispensed is within the rangeof the order, e.g. within the range of 2-10 mg for the current example.However, if there are a variety of different forms and/or amounts of themedication in the medication dispensing device, it may be confusing andtedious for a healthcare professional to select which of the variousmedication items they should access to minimize waste, e.g. one 5 mgvial and one 2 mg vial for a 7 mg dose, etc. Furthermore, the healthcarefacility's ability to discretely control the healthcare professional'saccess to the medications may be significantly reduced for variable doseorders, since the healthcare professional may be able to access moremedication than they will be administering to the patient.

SUMMARY

One or more embodiments relate to a system for dose dispensing. Thesystem including one or more processors and a memory includinginstructions. The instructions when executed by the one or moreprocessors, cause the one or more processors to secure a first containerincluding a medication in a first location within an automateddispensing device, the first container including a first amount of themedication, secure a second container including the medication in asecond location within the automated dispensing device, the secondcontainer including a second amount of the medication, receive aselection identifying an order for the medication, the order includingat least a maximum amount to administer, determine that the first amountand the second amount are sufficient to provide the maximum amount,determine that a first waste amount after administering the maximumamount from the first container is less than a second waste amount afteradministering the maximum amount from the second container, and activatethe automated dispensing device to permit access to the first location.

One or more embodiments relate to a system for dose dispensing. thesystem including one or more processors and a memory includinginstructions. The instructions when executed by the one or moreprocessors, cause the one or more processors to secure a first containerincluding a medication in a first location within an automateddispensing device, the first container including a first amount of themedication, secure a second container including the medication in asecond location within the automated dispensing device, the secondcontainer including a second amount of the medication, receive aselection identifying an order for the medication, the order includingat least a maximum amount to administer, determine that the first amountand the second amount are sufficient to provide the maximum amount,determine that a first waste amount after administering the maximumamount from the first container is the same as a second waste amountafter administering the maximum amount from the second container,determine that the first amount of the medication has a lower configureddispense order than the second amount of the medication, and activatethe automated dispensing device to permit access to the first location.

The disclosed subject matter relates to a method for variable dosedispensing. The method may include receiving a request for a variabledose order of a medication, requesting an amount of the medication to beadministered, and receiving, in response to the requesting, anindication of the amount of the medication to be administered. Themethod may further include determining, by a processor, at least oneitem of a plurality of items in a local inventory, the at least one itemcomprising at least the amount of the medication to be administered, anddispensing the at least one item.

The disclosed subject matter also relates to a machine-readable mediumembodying instructions that, when executed by a machine, allow themachine to perform a method for managing variable dose dispensing. Themethod may include receiving, from a medication dispensing device, auser identifier associated with a user, a dispensed amount of amedication, and an amount of the medication to be administered by theuser, wherein the dispensed amount exceeds the amount to be administeredby a waste amount. The method may further include initiating, inresponse to the receiving, a timer associated with the user identifierand the medication, and if, before the timer reaches a timeoutthreshold, an indication is received from a waste device that indicatesthat the user associated with the user identifier wasted the wasteamount of the medication, storing the indication, otherwise storing anotification that the user associated with the user identifier failed towaste the waste amount before the timer reached the timeout threshold.

The disclosed subject matter also relates to a system for managingvariable dose dispensing. The system includes one or more processors anda memory including instructions that, when executed by the one or moreprocessors, cause the one or more processors to: provide a list offormulary items, receive a selection of one of the formulary items,receive a first indication of an amount of another of the formularyitems that is an equivalency to the one of the formulary items, store afirst association between the amount of the another of the formularyitems and the one of the formulary items, and transmit the firstassociation to a medication dispensing device.

It is understood that other configurations of the subject technologywill become readily apparent to those skilled in the art from thefollowing detailed description, wherein various configurations of thesubject technology are shown and described by way of illustration. Aswill be realized, the subject technology is capable of other anddifferent configurations and its several details are capable ofmodification in various other respects, all without departing from thescope of the subject technology. Accordingly, the drawings and detaileddescription are to be regarded as illustrative in nature and not asrestrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain features of the subject technology are set forth in the appendedclaims. However, for purpose of explanation, several embodiments of thesubject technology are set forth in the following figures.

FIG. 1 illustrates an example hospital network environment in which avariable dose dispensing system may be implemented in accordance withone or more embodiments.

FIG. 2 illustrates a flow diagram of an example process for a medicationdispensing device in a variable dose dispensing system in accordancewith one or more embodiments.

FIG. 3 illustrates a flow diagram of an example item selection processfor a medication dispensing device in a variable dose dispensing systemin accordance with one or more embodiments.

FIG. 4 illustrates a flow diagram of an example item management processin a variable dose dispensing system in accordance with one or moreembodiments.

FIG. 5 illustrates a flow diagram of an example item configurationprocess in a variable dose dispensing system in accordance with one ormore embodiments.

FIG. 6 illustrates an example medication dispensing device that mayimplement a variable dose dispensing system in accordance with one ormore embodiments.

FIG. 7 conceptually illustrates an electronic system with which one ormore embodiments of the subject technology may be implemented.

DETAILED DESCRIPTION

The detailed description set forth below is intended as a description ofvarious configurations of the subject technology and is not intended torepresent the only configurations in which the subject technology may bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a thorough understandingof the subject technology. However, it will be clear and apparent tothose skilled in the art that the subject technology is not limited tothe specific details set forth herein and may be practiced using one ormore embodiments. In one or more instances, well-known structures andcomponents are shown in block diagram form in order to avoid obscuringthe concepts of the subject technology.

The subject variable dose dispensing system may allow a healthcarefacility, such as a hospital, to minimize the amount of medicationwasted when dispensing variable dose orders. In addition, the subjectvariable dose dispensing system may simplify the dispensing of variabledoses for healthcare professionals by determining which items should beused by the healthcare professional to administer an identified amountof a medication. Furthermore, the subject variable dose dispensingsystem may allow a healthcare facility to discretely control healthcareprofessionals' access to medications of variable dose orders, and mayallow a healthcare facility to rapidly identify when a healthcareprofessional may have improperly accessed a given medication.

For exemplary purposes, the subject variable dose dispensing system isdiscussed herein with respect to the dispensing of variable dosemedications in a healthcare facility, e.g. hospital. However, thesubject variable dose dispensing system is not limited to dispensingvariable dose medications in a healthcare facility; the conceptsdiscussed herein are applicable to the dispensing of medications inother environments.

FIG. 1 illustrates an example hospital network environment 100 in whicha variable dose dispensing system may be implemented in accordance withone or more embodiments. Not all of the depicted components may berequired, however, and one or more embodiments may include additionalcomponents not shown in the figure. Variations in the arrangement andtype of the components may be made without departing from the spirit orscope of the claims as set forth herein. Additional, different or fewercomponents may be provided.

The network environment 100 may include a number of medical devices,such as one or more medication dispensing devices 140 and/or one or morewaste devices 150, that may be communicably coupled to one another andto one or more of a management server 110 and/or a pharmacy server 120,such as by the network 130. In addition, there may be a number of otherdevices connected to the network 130, such as additional medicaldevices, additional servers, computing devices, mobile devices, etc.

The network 130 may be a public communication network (such as theInternet, cellular data network, dialup modems over a telephone network)or a private communications network (such as private local area network(“LAN”), leased lines). The network 130 may also include, but is notlimited to, any one or more of the following network topologies,including a bus network, a star network, a ring network, a mesh network,a star-bus network, a tree or hierarchical network, and the like. Theconnections may be wired or wireless.

The one or more medication dispensing devices 140 may be devices thatstore and dispenses medications, such as at a nurse's station. In one ormore embodiments, one or more of the medication dispensing devices 140may be a Pyxis MedStation™ Automated Dispensing Machine (ADM). The wastedevices 150 may be devices that accept and store wasted medications,e.g. excess medications, from healthcare professionals and track theamount of medications wasted by healthcare professionals. In one or moreembodiments, one or more of the waste devices 150 may be a PyxisEcoStation™ system.

In one or more embodiments, one or more of the medication dispensingdevices 140 and/or the waste devices 150 may include a processingdevice, such as a processor, and a memory. The processing deviceexecutes computer instructions stored in the memory, such as toimplement one or more processes of the subject variable dose dispensingsystem. In one or more examples, the computer instructions may be storedon a non-transitory computer-readable medium. One or more of themedication dispensing devices 140 and/or the waste devices 150 may be,or may include, the medication dispensing device 600 discussed belowwith respect to FIG. 6 and/or the electronic system 700 discussed belowwith respect to FIG. 7. Thus, in one or more embodiments, a medicationdispensing device 140 and a waste device 150 may be combined in a singledevice.

In one example, the management server 110 and/or the pharmacy server 120may be single computing devices such as computer servers and/or themanagement server 110 and the pharmacy server 120 may be a singlemachine. In another example, the management server 110 and/or thepharmacy server 120 may represent one or more separate computing devices(such as a cloud of computers and/or a distributed system) that arecommunicatively coupled, such as communicatively coupled over thenetwork 130, that collectively, or individually, perform one or moreserver-side functions. In this example, the one or more computingdevices of the management server 110 and/or the pharmacy server 120 maybe geographically collocated and/or disparately located. The managementserver 110 and/or pharmacy server 120 may be coupled with variousdatabases, storage services, or other computing devices.

In one or more embodiments, the management server 110 includes aprocessing device 112 and a data store 114. The processing device 112executes computer instructions stored in the data store 114, such as toimplement one or more processes of the subject variable dose dispensingsystem. In one or more examples, the data store 114 may store thecomputer instructions on a non-transitory computer-readable medium. Inone or more embodiments, the pharmacy server 120 includes a processingdevice 122 and a data store 124. The processing device 122 executescomputer instructions stored in the data store 124, such as to implementone or more processes of the subject variable dose dispensing system. Inone or more examples, the data store 124 may store the computerinstructions on a non-transitory computer-readable medium. In one ormore embodiments, the management server 110 and/or the pharmacy server120 may be, or may include, the electronic system 700 discussed belowwith respect to FIG. 7.

In operation, one or more of the medication dispensing devices 140 mayimplement one or more aspects of the subject variable dose dispensingsystem, such as by performing one or more of the example processes thatare discussed further below with respect to FIGS. 2 and 3. In addition,one or more of the management server 110 and/or the pharmacy server 120may implement one or more aspects of the subject variable dosedispensing system, such as by performing one or more of the exampleprocesses that are discussed further below with respect to FIGS. 4 and5.

FIG. 2 illustrates a flow diagram of an example process 200 for amedication dispensing device in a variable dose dispensing system inaccordance with one or more embodiments. For explanatory purposes, theexample process 200 is described herein with reference to one or more ofthe devices 140, 150 and/or servers 110, 120 of the example hospitalnetwork environment 100 of FIG. 1; however, the example process 200 isnot limited to the devices 140, 150 and/or servers 110, 120 of theexample hospital network environment 100 of FIG. 1. Further forexplanatory purposes, the blocks of the example process 200 aredescribed herein as occurring in serial fashion, or linearly. However,multiple blocks of the example process 200 may occur in parallel. Inaddition, the blocks of the example process 200 need not be performed inthe order shown and/or one or more of the blocks of the example process200 need not be performed.

In block 202, a medication dispensing device 140 receives a variabledose order from a pharmacy, such as from the pharmacy server 120 overthe network 130. In one or more embodiments, the variable dose order mayindicate a medication, e.g. one or more medications of the same puregeneric name or generic name, and a range of amounts of the medicationthat may be administered by a healthcare professional to a patient, suchas 2-10 mg of morphine. In one or more embodiments, the variable doseorder may also include an indication of the dosage form of themedication to be administered, e.g. tablet, caplet, etc. Alternatively,or in addition, the variable dose order may include an identifier of avariable dose group that is associated with the variable dose order,such as a med identifier. In this instance, the variable dose order mayor may not indicate a medication, a range, and/or a dosage form. If thevariable dose order does not include a range to be administered, themedication dispensing device 140 may use a range and dose unit that isdefined for the variable dose order, as discussed further below withrespect to FIG. 5.

In block 204, the medication dispensing device 140 receives a selectionof a variable dose order from a user, such as a healthcare professional.For example, a healthcare professional may authenticate with themedication dispensing device 140, such as by providing logincredentials, and the medication dispensing device 140 may display a listof orders that the healthcare professional is authorized to access. Thehealthcare professional may then select a variable dose order for amedication from the displayed list, such as a variable dose order for2-10 mg of morphine every six hours.

In block 206, the medication dispensing device 140 requests that thehealthcare professional input the amount of the medication of thevariable dose order that will be administered to the patient. In block208, the medication dispensing device 140 receives an indication of theamount to be administered from the healthcare professional, such as 7 mgof morphine for a 2-10 mg variable dose order of morphine. For example,the healthcare professional may type in an amount to be administered,such as using a keyboard, or may indicate the amount to be administeredvia a touch screen or other input device. In block 210, the medicationdispensing device 140 determines whether the amount of the medication tobe administered by the healthcare professional is within the range ofthe variable dose order. For example, 7 mg of morphine would be withinthe range of a 2-10 mg variable dose order of morphine, while 11 mg ofmorphine would not be within the range.

If, in block 210, the medication dispensing device 140 determines thatthe amount to be administered is not within the range of the variabledose order, the medication dispensing device 140 moves to block 212. Inblock 212, the medication dispensing device 140 provides an alert to thehealthcare professional, such as on a display, an audible alert, or anyother alert, that indicates that the amount to be administered is notwithin the range of the variable dose order. The medication dispensingdevice 140 then returns to block 206 and requests that the healthcareprofessional input a different amount to be administered. Alternatively,or in addition, the medication dispensing device 140 may not allow thehealthcare professional to input an amount to be administered that isoutside of the range of the variable dose order.

If, in block 210, the medication dispensing device 140 determines thatthe amount to be administered is within the range of the variable doseorder, the medication dispensing device 140 moves to block 214. In block214, the medication dispensing device 140 determines one or more itemsto dispense based at least in part on the available inventory of themedication dispensing device 140 and the amount of the medication to beadministered, e.g. as indicated by the healthcare professional. In oneor more embodiments, the medication dispensing device 140 may determinethe items to dispense such that the amount of wasted medication from thedispensed items will be minimized. An example process that may beimplemented by the medication dispensing device 140 to determine whichitems to dispense is discussed further below with respect to FIG. 3

In one or more embodiments, the medication dispensing device 140 mayreceive, e.g. from the pharmacy server 120, an indication of a variabledose group that is associated with the variable dose order. The variabledose group may list the items that can be dispensed by the medicationdispensing device 140 to fill the variable dose order. For example, avariable dose group that is associated with variable dose orders for2-10 mg of morphine may include vials that contain various amounts ofmorphine, e.g. 2 mg, 5 mg, etc. In this instance, the medicationdispensing device 140 may fill a variable dose order by dispensing itemsthat are included in the variable dose group, e.g. such that the amountof wasted medication from the dispensed items will be minimized. Thecreation of exemplary variable dose groups, and the transmission thereofto medication dispensing devices 140, are discussed further below withrespect to FIG. 5.

In block 216, the medication dispensing device 140 dispenses thedetermined items. In block 218, the medication dispensing device 140displays an indication of any excess amount of the medication that wasdispensed, e.g. any amount of the medication that was dispensed inexcess of the amount to be administered. In one or more embodiments, theindication may further include an amount of time that the healthcareprofessional has to physically waste the excess amount before the excessamount will be identified as missing. In one or more embodiments, theexcess amount may be logged as undocumented waste immediately if theuser does not waste the excess amount at the time the medication isremoved from the medication dispensing device 140. However, the user maystill be given an amount of time to physically waste the excess amountbefore an alert or notification is triggered.

In one or more embodiments, the amount of time that is provided to thehealthcare professional to physically waste the excess amount may bebased on one or more of: characteristics of the dispensed medication,characteristics of the dosage form of the dispensed medication,characteristics regarding the manner in which the dispensed medicationwill be administered, and/or characteristics regarding the condition ofthe patient receiving the dispensed medication. For example, thehealthcare professional may be provided with a longer period of time towaste excess medication from a bag of liquid that is to be infused intoa patient as compared to a syringe that is to be injected into thepatient. In one or more embodiments, the medication dispensing device140 may determine the amount of time that the healthcare professionalhas to waste the medication. Alternatively, or in addition, themedication dispensing device 140 may receive the amount of time from aserver, such as from the management server 110. In one or moreembodiments, the timer may be set to zero if the excess amount is loggedas missing if the user does not waste the excess amount at the time themedication is removed from the medication dispensing device 140.

In block 220, the medication dispensing device 140 transmits, such as tothe management server 110, the identifier of the healthcareprofessional, an indication of the one or more items that weredispensed, and at least one of an indication of the amount to beadministered and/or an indication of any excess amount that wasdispensed. Alternatively, or in addition, if the medication dispensingdevice 140 determined the amount of time that the healthcareprofessional has to waste any excess amount of the medication, themedication dispensing device 140 may transmit the amount of time to themanagement server 110.

FIG. 3 illustrates a flow diagram of an example item selection process300 for a medication dispensing device in a variable dose dispensingsystem in accordance with one or more embodiments. For explanatorypurposes, the example item selection process 300 is described hereinwith reference to one or more of the devices 140, 150 and/or servers110, 120 of the example hospital network environment 100 of FIG. 1;however, the item selection process 300 is not limited to the devices140, 150 and/or servers 110, 120 of the example hospital networkenvironment 100 of FIG. 1. Further for explanatory purposes, the blocksof the example item selection process 300 are described herein asoccurring in serial fashion, or linearly. However, multiple blocks ofthe example item selection process 300 may occur in parallel. Inaddition, the blocks of the example item selection process 300 need notbe performed in the order shown and/or one or more of the blocks of theexample item selection process 300 need not be performed.

In block 302, a medication dispensing device 140 receives an indicationof an amount of a medication that is to be administered to a patient fora previously selected order, such as a variable dose order. The amountof the medication may have been previously verified as being within arange of the selected variable dose order. Alternatively, or inaddition, the selected order may be a zero dose order for a medicationthat does not contain a range of dispensable amounts. In this instance,the medication dispensing device 140 may dispense any amount of themedication that is requested by a user, such as a healthcareprofessional.

In block 304, the medication dispensing device 140 determines whetherthe amount and/or dosage form of the medication to be administered isavailable in the inventory of the medication dispensing device 140. Forexample, if the medication dispensing device 140 received a variabledose group that is associated with the variable dose order, themedication dispensing device 140 may determine whether one or more itemsof the variable dose group are available in inventory that satisfy theamount and/or dosage form of the medication to be administered.

If, in block 304, the medication dispensing device 140 determines thatthe amount of the medication to be administered is available in theinventory of the medication dispensing device 140, the medicationdispensing device 140 moves to block 306. In block 306, the medicationdispensing device 140 determines one or more items in inventory thatmatch the dosage form of the variable dose order (or in the same dosageform group) and satisfy the requested amount with the lowest itemquantity without splitting the item when the medication dispensingdevice 140 is configured not to split. For example, a healthcareprofessional may indicate that 7 mg of morphine will be administered fora variable dose order of 2-10 mg of morphine in vial form, and themedication dispensing device 140 may have two vials of 4 mg, one vial of8 mg and one vial of 9 mg that are available in inventory. In thisexample, the two vials of 4 mg of morphine (based on equivalencies asdiscussed further below), the one vial of 8 mg of morphine, and the onevial of 9 mg of morphine would each satisfy the amount to beadministered and be within the range of the variable dose order.However, the one vial of 8 mg of morphine and the one vial of 9 mg ofmorphine would have a lower item quantity than the two vials of 4 mg ofmorphine. Thus, in this instance the medication dispensing device woulddetermine that either the one vial of 8 mg of morphine or the one vialof 9 mg of morphine could properly fulfill the order.

In block 308, the medication dispensing device 140 determines whethermore than one item, or group of items, meets the criteria used in block306, e.g. whether more than one item, or group of items, were identifiedin block 306 as being able to properly fulfilling the order. If, inblock 308, the medication dispensing device 140 determines that there isonly one item that meets the criteria of block 306, the medicationdispensing device 140 moves to block 312. In block 312, the medicationdispensing device 140 dispenses the item determined in block 306.

If, in block 308, the medication dispensing device 140 determines thatthere is more than one item that satisfies the criteria of block 306,such as the 8 mg and 9 mg vials of morphine discussed in the exampleabove, the medication dispensing device 140 moves to block 310. In block310, the medication dispensing device 140 dispenses the item that willresult in the least amount of wasted medication, e.g. the item that hasan amount that is closest to the amount to be administered. For example,if the amount to be administered is 7 mg of morphine for a 2 mg-10 mgvariable dose order, and the medication dispensing device 140 containsan 8 mg vial and a 9 mg vial, the medication dispensing device 140dispenses the 8 mg vial since it will only result in 1 mg of waste asopposed to the 2 mg of waste that would result from dispensing the 9 mgvial. Alternatively, or in addition, if more than one item meets thecriteria and has the same dosage or in the same dosage form/group, themedication dispensing device 140 may dispense the item with the lowestconfigured dispense order. In one or more embodiments, the dispenseorder of the items may be configured by a pharmacy, as is discussedfurther below with respect to FIG. 5.

If, in block 304, the medication dispensing device 140 determines thatthe amount to be administered is not available in the inventory, themedication dispensing device 140 moves to block 314. In block 314, themedication dispensing device 140 determines whether the inventorycontains equivalencies of the medication for the amount to beadministered. For example, the medication dispensing device 140 mayreceive, from a pharmacy server 120, an indication of one or more itemsthat are equivalencies of another item, e.g. two 2 mg vials of morphinemay be indicated as an equivalency of one 4 mg vial of morphine. Thecreation of exemplary equivalencies, and the transmission thereof tomedication dispensing devices 140, are discussed further below withrespect to FIG. 5.

In one or more embodiments, the medication dispensing device 140 mayconsider an ordered medication's equivalencies when one or more of thefollowing criteria are satisfied: the ordered item results in an invalidamount, e.g. a fractional amount, the ordered item is inactive, theordered item is not loaded, the ordered item is out of stock, there isinsufficient quantity of the ordered item, or there is not indirectaccess for the healthcare professional based on the drawer that the itemis in, as discussed further below with respect to FIG. 6.

If, in block 314, the medication dispensing device 140 determines thatthe amount to be administered can be provided through one or moreequivalencies of the medication, the medication dispensing device 140moves to block 306. Alternatively, or in addition, the medicationdispensing device 140 may perform the equivalencies determination atblock 304. In this instance, the medication dispensing device 140 maymove directly to block 316 (skipping block 314), if the medicationdispensing device 140 determines that the amount to be administered isnot available in inventory and can not be provided through equivalenciesof the medication. In one or more embodiments, if there are multipleequivalences available, the medication dispensing device 140 maydispense the equivalency that results in no wasted medication and nomore than three items dispensed, or that results in the least number ofitems dispensed.

If, in block 314, the medication dispensing device 140 determines thatthe amount to be administered can not be provided through equivalencies,the medication dispensing device 140 moves to block 316. In block 316,the medication dispensing device 140 provides an indication that theamount to be administered is not available in the inventory of themedication dispensing device 140. In block 318, the medicationdispensing device 140 receives an indication, such as from themanagement server 110, of the nearest medication dispensing device 140that can provide the healthcare professional with the amount of themedication to be administered, e.g. in the form of the orderedmedication and/or through equivalencies. In block 320, the medicationdispensing device 140 displays an indication of the nearest medicationdispensing device 140 that can provide the amount to be administered.The medication dispensing device 140 may further display the location ofthe nearest medication dispensing device 140 that can provide the amountto be administered, such as on a map of the healthcare facility.Alternatively, or in addition, the medication dispensing device 140 maydisplay instructions for navigating to the nearest medication dispensingdevice 140 that can provide the amount to be administered. In one ormore embodiments, the medication dispensing device 140 may also transmitthe directions to a mobile device of the healthcare professional, suchas over the network 130 or over a local area network connection, e.g. aBluetooth connection.

FIG. 4 illustrates a flow diagram of an example item management process400 in a variable dose dispensing system in accordance with one or moreembodiments. For explanatory purposes, the example item managementprocess 400 is described herein with reference to one or more of thedevices 140, 150 and/or servers 110, 120 of the example hospital networkenvironment 100 of FIG. 1; however, the example item management process400 is not limited to the devices 140, 150 and/or servers 110, 120 ofthe example hospital network environment 100 of FIG. 1. Further forexplanatory purposes, the blocks of the example item management process400 are described herein as occurring in serial fashion, or linearly.However, multiple blocks of the example item management process 400 mayoccur in parallel. In addition, the blocks of the example itemmanagement process 400 need not be performed in the order shown and/orone or more of the blocks of the example item management process 400need not be performed.

In block 402, a server, such as the management server 110, receives,such as from a medication dispensing device 140, an indication of anamount of a medication that was dispensed to a healthcare professional,an amount that the healthcare professional indicated would beadministered, and an identifier of the healthcare professional. In oneor more embodiments, the amount that the healthcare professionalindicated would be administered may be less than the amount that wasdispensed, and the difference between the two may be referred to as anamount to be wasted, a waste amount, or an excess amount. Alternatively,or in addition, the management server 110 may receive an indication ofthe amount dispensed, the amount to be wasted, and the identifier of thehealthcare professional. The management server 110 may store thereceived information, such as in data store 114. In block 403, themanagement server 110 initiates a timer with respect to the itemdispensed and the user identifier. The management server 110 may utilizethe timer to determine when the healthcare professional has exceeded theamount of time allotted for wasting the additional amount of themedication that was dispensed. In one or more embodiments, themanagement server 110 may concurrently manage multiple timers for thesame healthcare professional, e.g. for different medications accessed bythe healthcare professional at different times and/or for multiplehealthcare professionals.

In block 404, the management server 110 determines whether an indicationthat the healthcare professional wasted an amount of the medication wasreceived, such as from a waste device 150. For example, a healthcareprofessional may dispose of an amount of excess medication in a wastedevice 150. The healthcare professional may provide their logincredentials to the waste device 150 such that the waste device 150 canassociate the healthcare professional with the amount of the medicationthat was wasted. In one or more embodiments, the waste device 150 mayautomatically determine the amount of the medication that was wasted,e.g. by using an item counter, such as a pill counter, by measuring avolume of liquid wasted, by determining a weight of a disposed item andcomparing the measured weight to a per unit weight of the disposed item,etc. Alternatively, or in addition, the healthcare professional mayinput the type of medication and/or the amount of the medication thatwas wasted. Alternatively, or in addition, the waste device 150 mayrequire that the healthcare professional have a witness while they wastethe excess amount, and the witness may also be required to provide theirlogin credentials to the waste device 150.

If, in block 404, the management server 110 determines that theindication has not been received, the management server 110 moves toblock 410. In block 410, the management server 110 determines whetherthe timer exceeds the timeout threshold, e.g the amount of time allottedfor the healthcare professional to waste the excess amount of thedispensed medication. If, in block 410, the management server 110determines that the timer does not exceed the timeout threshold, themanagement server 110 returns to block 404 and determines whether theindication has been received.

If, in block 410, the management server 110 determines that the timerhas exceeded the timeout threshold, the management server 110 moves toblock 412. In block 412, the management server 110 stores an indicationof the amount of the medication that was not wasted along with theidentifier of the healthcare professional. In block 414, the managementserver 110 transmits a notification that the medication has not beenwasted, such as to a supervisor of the healthcare professional, to asecurity personnel, etc. In one or more examples, the notification mayalso be transmitted to the medication dispensing devices 140 and mayfurther indicate to the medication dispensing devices 140 that noadditional medication should be dispensed to the healthcareprofessional. Alternatively, or in addition, the notification may betransmitted to an access control system for the healthcare facility andmay further indicate to the access control system that the accessprivileges of the healthcare professional, e.g. via a badge, should berevoked. In this manner the healthcare professional may be preventedfrom leaving the healthcare facility with the amount of the medicationthat was not wasted.

If, in block 404, the management server 110 determines that it receivedthe indication that the healthcare professional has wasted an amount ofthe medication, the management server 110 moves to block 406. In block406, the management server 110 determines whether the amount that waswasted by the healthcare professional is greater than or equal to theexcess amount that was dispensed to the healthcare professional. If, inblock 406, the management server 110 determines that the amount themedication that was wasted by the healthcare professional is not greaterthan or equal to the excess amount of medication, the management server110 moves to block 410. If, in block 406, the management server 110determines that the amount of the medication that was wasted by thehealthcare professional is equal to or greater than the excess amount ofthe medication, the management server 110 moves to block 408. In block408, the management server 110 stores an indication, such as in datastore 114, that all of the excess medication that was dispensed to thehealthcare professional was wasted by the healthcare professional.

In one or more embodiments, the management server 110 may monitorwhether the healthcare professional administered the amount of themedication that the healthcare professional indicated would beadministered. For example, the management server 110 may be incommunication, over the network 130, with one or more additional medicaldevices, e.g. dispensing and/or infusion devices, such as pumps. Thedispensing and/or infusion devices may transmit an indication to themanagement server 110 of the amount of the medication that wasadministered by the healthcare professional to the patient. For example,an infusion pump, or a device coupled thereto, may require that thehealthcare professional provide their login credentials beforeprogramming the amount of medication that will be infused into thepatient. After infusing the medication into the patient, the infusionpump, or a device coupled thereto, may transmit to the management server110 the amount of the medication that was infused into the patient alongwith the user identifier of the healthcare professional.

In these one or more embodiments, the management server 110 may transmitthe notification of missing medication when the amount of medicationadministered to the patient is less than the amount that the healthcareprofessional indicated would be administered. Alternatively, or inaddition, the management server 110 may transmit the notification of themissing medication when the amount of the medication administered to thepatient plus the amount of wasted medication is less than the amount ofthe medication dispensed to the healthcare professional. In any of theaforementioned examples, the management server 110 may incorporate oneor more thresholds to account for de minimis losses of medication thatmay occur while the medication is being transported, administered, etc.

FIG. 5 illustrates a flow diagram of an example item configurationprocess 500 in a variable dose dispensing system in accordance with oneor more embodiments. For explanatory purposes, the example itemconfiguration process 500 is described herein with reference to one ormore of the devices 140, 150 and/or servers 110, 120 of the examplehospital network environment 100 of FIG. 1; however, the example itemconfiguration process 500 is not limited to the devices 140, 150 and/orservers 110, 120 of the example hospital network environment 100 ofFIG. 1. Further for explanatory purposes, the blocks of the example itemconfiguration process 500 are described herein as occurring in serialfashion, or linearly. However, multiple blocks of the example itemconfiguration process 500 may occur in parallel. In addition, the blocksof the example item configuration process 500 need not be performed inthe order shown and/or one or more of the blocks of the example itemconfiguration process 500 need not be performed.

In block 502, a server, such as the pharmacy server 120, may provide alist of formulary items to a user, such as a pharmacist. For example, apharmacist may interact with an application, such as a web application,a mobile application, or generally any computing application, providedby the pharmacy server, such as by using a computing device thatincludes a processor and a memory. In this example, the list offormulary items may be displayed to the user on the computing device. Inblock 504, the pharmacy server 120 receives a selection of one of thelisted formulary items. For example, a user may interact with theapplication provided by the pharmacy server 120 to select one of thelisted formulary items, and the computing device of the user maytransmit an indication of the selection to the pharmacy server 120.

In block 506, the pharmacy server 120 determines whether the user hasrequested to modify or add equivalencies for the selected item. Forexample, the user may interact with the application provided by thepharmacy server 120 to indicate that they would like to add or modifythe equivalencies of the selected item, and the computing device of theuser may transmit an indication of the same to the pharmacy server 120.If, in block 506, the pharmacy server 120 determines that the user hasrequested to modify the equivalencies of the selected item, the pharmacyserver 120 moves to block 508. In block 508, the pharmacy server 120receives an indication of amounts of one or more items in the list offormulary items that are equivalencies of the selected item. Forexample, the user may interact with the application provided by thepharmacy server 120 to indicate the amounts of one or more items in thelist of formulary items that are equivalencies of the selected item, andthe computing device of the user may transmit the indicated amounts tothe pharmacy server 120.

In one or more embodiments, the pharmacy server 120 may suggest itemsthat may be equivalents to the selected item. For example, each of theformulary items may be associated with a generic name, such as“morphine,” and the pharmacy server 120 may suggest items as equivalentsthat satisfy one or more of the following: have the same generic name asthe selected item, have the same dosage form as the selected item,and/or have an equivalency quantity that is below a threshold, e.g. theamount of the item that is equivalent to the selected item. In one ormore embodiments, if the selected item is defined by a strength, thepharmacy server 120 may suggest an item that may be an equivalent of aselected item based on one or more of the following: the strength of theitem and/or the strength of the selected item, whether the strength ofthe item is divisible by the strength of the selected item withoutresulting in fractional amounts, and/or the unit of measure of the itemand/or the selected item. In one or more embodiments, if the selecteditem is defined by a strength and a total volume, the pharmacy server120 may suggest items as equivalents that have a derived concentrationbased on the strength and total volume.

In one or more embodiments, if a selected item is defined by a totalvolume, the pharmacy server 120 may suggest items as equivalents thatsatisfy one or more of the following: have a total volume, have a volumeamount that is divisible into the selected item's without resulting infractional amounts, and/or have the same unit of volume or sameconfigured base unit as the selected item. In one or more embodiments,if the selected item is defined by a concentration, the pharmacy server120 may suggest items as equivalents that satisfy one or more of thefollowing criteria: have the same concentration as the selected item,have a concentration strength that is divisible into the selected item'sstrength without resulting in fractional amounts, have a concentrationstrength with the same unit of measure or same configured base unit asthe selected item, and/or have a concentration volume with a sameinternal volume or same configured base unit as the selected item.

In block 510, the pharmacy server 120 stores an association between theitem and each of the indicated equivalencies, such as in the data store124. If, in block 506, the pharmacy server 120 determines that the userhas not indicated that they would like to modify the equivalencies ofthe selected item, the pharmacy server 120 moves to block 512. In one ormore embodiments, the pharmacy server 120 may remove an item as anequivalency of the selected item if the information that matched theitems changes, e.g. the generic name of either item.

In block 512, the pharmacy server 120 determines whether the user hasrequested to associate the selected item with one or more variable dosegroups. For example, the user may interact with the application providedby the pharmacy server 120 to indicate that they would like to associatethe selected item with one or more variable dose groups, and thecomputing device of the user may transmit an indication of the same tothe pharmacy server 120. If, in block 512, the pharmacy server 120determines that the user has requested to associate the selected itemwith one or more variable dose groups, the pharmacy server 120 moves toblock 514.

In block 514, the pharmacy server 120 may receive an indication of oneor more variable dose groups that the user would like to associate withthe selected item. For example, the user may interact with theapplication provided by the pharmacy server 120 to indicate the one ormore variable dose groups, and the computing device of the user maytransmit the indicated variable dose groups to the pharmacy server 120.In block 516, the pharmacy server 120 stores an association between theitem and each of the indicated variable dose groups, such as in the datastore 124. In one or more embodiments, the user may also associate adosage range with the variable dose group, such as 2-10 mg.

In block 518, the pharmacy server 120 transmits the equivalencies of theselected item, and/or the variable dose groups associated with theselected item, to one or more medication dispensing devices 140, such asacross one or more healthcare facilities. For example, the pharmacyserver 120 may transmit the equivalencies and variable dose groupassociations to one or more of the medication dispensing devices 140that are stocked by the pharmacy. In one or more embodiments, thepharmacy server 120 may transmit the stored equivalencies and variabledose groups on a periodic basis, such as an hourly basis, a daily basis,a weekly basis, etc. Alternatively, or in addition, the pharmacy server120 may transmit equivalencies and variable dose groups as they areindicated by a user.

FIG. 6 illustrates an example medication dispensing device 600 that mayimplement a variable dose dispensing system in accordance with one ormore embodiments. Not all of the depicted components may be required,however, and one or more embodiments may include additional componentsnot shown in the figure. Variations in the arrangement and type of thecomponents may be made without departing from the spirit or scope of theclaims as set forth herein. Additional, different or fewer componentsmay be provided.

The medication dispensing device 600 may include a display 610 and oneor more drawers 620. The one or more drawers 620 may include one or morereceptacles 630, that may each contain one or more medication items. Thedisplay 610 of the medication dispensing device 600 may be a touchscreen and/or the medication dispensing device 600 may include a userinput device, such as a keyboard, a pointing device, etc.

In operation, a user may interact with the medication dispensing device600, such as by using the display 610 (in the case of a touch screen orsimilar technology), or using a separate human input device, such as akeyboard or a pointing device. The drawers 620 of the medicationdispensing device 600 may all be closed and/or locked when the userfirst interacts with the medication dispensing device 600. The user mayprovide login credentials to the medication dispensing device 600 andthe medication dispensing device 600 may authenticate the user based onthe credentials. The medication dispensing device 600 may then display alist of orders to the user, such as on the display. The orders displayedto the user may be determined based on the login credentials provided bythe user. For example, the user may be associated with a particular areaof a hospital and the orders displayed to the user may be for patientswho are located in the area that of the hospital that is associated withthe user.

The user may select a variable dose order from the list of displayedorders, such as by using the display 610 or a separate user inputdevice. Upon receiving the user's selection, the medication dispensingdevice 600 may request that the user indicate the amount of the orderthat will be administered to the patient. The user may input the amountto be administered, the medication dispensing device 600 may verify thatthe amount is within a range of the variable dose order, and themedication dispensing device 600 may determine one or more items ininventory that contain the amount to be administered and minimize theamount that will be dispensed and/or wasted. The medication dispensingdevice 600 may open one or more drawers 620 storing one or morereceptacles 630 that contain the determined one or more items. Themedication dispensing device 600 may also open and/or release the one ormore receptacles such that the user may access the items containedtherein.

In one or more examples, the items contained in the receptacles 630 mayeach include an identifier, such as a bar code or a radio frequencyidentifier (RFID). The identifiers of the items may be used to ensurethat the user does not retrieve more than the dispensed amount of anitem from a receptacle 630, such as in instances when a receptacle 630includes more than the dispensed amount of a particular item. Forexample, the medication dispensing device 600 may automatically trackeach item that is removed from a given receptacle based on the RFID ofthe removed items, and/or other item tracking mechanisms

The medication dispensing device 600 may store an indication of theamount of the medication dispensed and the user identifier of the userto whom the medication was dispensed. If the amount of the medicationdispensed exceeded the amount to be administered, the medicationdispensing device 600 may display an indication of the excess amount ofthe medication that is to be wasted by the user, such as on the display610. The medication dispensing device 600 may also display an amount oftime that the user has to waste the excess amount before the excessamount will be identified as missing.

The medication dispensing device 600 may transmit to an external server,such as the management server 110, the identifier of the user, theamount dispensed, and the amount to be wasted, if any. The medicationdispensing device 600 may also transmit the time allotted for wastingthe excess amount to the external server if the time allotted wasdetermined by the medication dispensing device 600.

FIG. 7 conceptually illustrates electronic system 700 with which one ormore embodiments of the subject technology may be implemented.Electronic system 700, for example, can be a medication dispensingdevice 140, a waste device 150, a server 110, 120, a desktop computer, alaptop computer, a tablet computer, a phone, a personal digitalassistant (PDA), or generally any electronic device that transmitssignals over a network. Such an electronic system includes various typesof computer readable media and interfaces for various other types ofcomputer readable media. Electronic system 700 includes bus 708,processing unit(s) 712, system memory 704, read-only memory (ROM) 710,permanent storage device 702, input device interface 714, output deviceinterface 706, and network interface 716, or subsets and variationsthereof.

Bus 708 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices ofelectronic system 700. In one or more embodiments, bus 708communicatively connects processing unit(s) 712 with ROM 710, systemmemory 704, and permanent storage device 702. From these various memoryunits, processing unit(s) 712 retrieves instructions to execute and datato process in order to execute the processes of the subject disclosure.The processing unit(s) can be a single processor or a multi-coreprocessor in different embodiments.

ROM 710 stores static data and instructions that are needed byprocessing unit(s) 712 and other modules of the electronic system.Permanent storage device 702, on the other hand, is a read-and-writememory device. This device is a non-volatile memory unit that storesinstructions and data even when electronic system 700 is off. One ormore embodiments of the subject disclosure use a mass-storage device(such as a magnetic or optical disk and its corresponding disk drive) aspermanent storage device 702.

Other embodiments use a removable storage device (such as a floppy disk,flash drive, and its corresponding disk drive) as permanent storagedevice 702. Like permanent storage device 702, system memory 704 is aread-and-write memory device. However, unlike storage device 702, systemmemory 704 is a volatile read-and-write memory, such as random accessmemory. System memory 704 stores any of the instructions and data thatprocessing unit(s) 712 needs at runtime. In one or more embodiments, theprocesses of the subject disclosure are stored in system memory 704,permanent storage device 702, and/or ROM 710. From these various memoryunits, processing unit(s) 712 retrieves instructions to execute and datato process in order to execute the processes of one or more embodiments.

Bus 708 also connects to input and output device interfaces 714 and 706.Input device interface 714 enables a user to communicate information andselect commands to the electronic system. Input devices used with inputdevice interface 714 include, for example, alphanumeric keyboards andpointing devices (also called “cursor control devices”). Output deviceinterface 706 enables, for example, the display of images generated byelectronic system 700. Output devices used with output device interface706 include, for example, printers and display devices, such as a liquidcrystal display (LCD), a light emitting diode (LED) display, an organiclight emitting diode (OLED) display, a flexible display, a flat paneldisplay, a solid state display, a projector, or any other device foroutputting information. One or more embodiments may include devices thatfunction as both input and output devices, such as a touchscreen. Inthese embodiments, feedback provided to the user can be any form ofsensory feedback, such as visual feedback, auditory feedback, or tactilefeedback; and input from the user can be received in any form, includingacoustic, speech, or tactile input.

Finally, as shown in FIG. 7, bus 708 also couples electronic system 700to a network (not shown) through network interface 716. In this manner,the computer can be a part of a network of computers (such as a localarea network (“LAN”), a wide area network (“WAN”), or an Intranet, or anetwork of networks, such as the Internet. Any or all components ofelectronic system 700 can be used in conjunction with the subjectdisclosure.

Many of the above-described features and applications may be implementedas software processes that are specified as a set of instructionsrecorded on a computer readable storage medium (alternatively referredto as computer-readable media, machine-readable media, ormachine-readable storage media). When these instructions are executed byone or more processing unit(s) (e.g., one or more processors, cores ofprocessors, or other processing units), they cause the processingunit(s) to perform the actions indicated in the instructions. Examplesof computer readable media include, but are not limited to, RAM, ROM,read-only compact discs (CD-ROM), recordable compact discs (CD-R),rewritable compact discs (CD-RW), read-only digital versatile discs(e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritableDVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SDcards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid statehard drives, ultra density optical discs, any other optical or magneticmedia, and floppy disks. In one or more embodiments, the computerreadable media does not include carrier waves and electronic signalspassing wirelessly or over wired connections, or any other ephemeralsignals. For example, the computer readable media may be entirelyrestricted to tangible, physical objects that store information in aform that is readable by a computer. In one or more embodiments, thecomputer readable media is non-transitory computer readable media,computer readable storage media, or non-transitory computer readablestorage media.

In one or more embodiments, a computer program product (also known as aprogram, software, software application, script, or code) can be writtenin any form of programming language, including compiled or interpretedlanguages, declarative or procedural languages, and it can be deployedin any form, including as a stand alone program or as a module,component, subroutine, object, or other unit suitable for use in acomputing environment. A computer program may, but need not, correspondto a file in a file system. A program can be stored in a portion of afile that holds other programs or data (e.g., one or more scripts storedin a markup language document), in a single file dedicated to theprogram in question, or in multiple coordinated files (e.g., files thatstore one or more modules, sub programs, or portions of code). Acomputer program can be deployed to be executed on one computer or onmultiple computers that are located at one site or distributed acrossmultiple sites and interconnected by a communication network.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, one or more embodiments areperformed by one or more integrated circuits, such as applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In one or more embodiments, such integrated circuits executeinstructions that are stored on the circuit itself.

Those of skill in the art would appreciate that the various illustrativeblocks, modules, elements, components, methods, and algorithms describedherein may be implemented as electronic hardware, computer software, orcombinations of both. To illustrate this interchangeability of hardwareand software, various illustrative blocks, modules, elements,components, methods, and algorithms have been described above generallyin terms of their functionality. Whether such functionality isimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.Skilled artisans may implement the described functionality in varyingways for each particular application. Various components and blocks maybe arranged differently (e.g., arranged in a different order, orpartitioned in a different way) all without departing from the scope ofthe subject technology.

It is understood that any specific order or hierarchy of blocks in theprocesses disclosed is an illustration of example approaches. Based upondesign preferences, it is understood that the specific order orhierarchy of blocks in the processes may be rearranged, or that allillustrated blocks be performed. Any of the blocks may be performedsimultaneously. In one or more embodiments, multitasking and parallelprocessing may be advantageous. Moreover, the separation of varioussystem components in the embodiments described above should not beunderstood as requiring such separation in all embodiments, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

As used herein, the phrase “at least one of” preceding a series ofitems, with the term “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list (i.e.,each item). The phrase “at least one of” does not require selection ofat least one of each item listed; rather, the phrase allows a meaningthat includes at least one of any one of the items, and/or at least oneof any combination of the items, and/or at least one of each of theitems. By way of example, the phrases “at least one of A, B, and C” or“at least one of A, B, or C” each refer to only A, only B, or only C;any combination of A, B, and C; and/or at least one of each of A, B, andC.

The predicate words “configured to”, “operable to”, and “programmed to”do not imply any particular tangible or intangible modification of asubject, but, rather, are intended to be used interchangeably. In one ormore embodiments, a processor configured to monitor and control anoperation or a component may also mean the processor being programmed tomonitor and control the operation or the processor being operable tomonitor and control the operation. Likewise, a processor configured toexecute code can be construed as a processor programmed to execute codeor operable to execute code.

A phrase such as “an aspect” does not imply that such aspect isessential to the subject technology or that such aspect applies to allconfigurations of the subject technology. A disclosure relating to anaspect may apply to all configurations, or one or more configurations.An aspect may provide one or more examples of the disclosure. A phrasesuch as an “aspect” may refer to one or more aspects and vice versa. Aphrase such as an “embodiment” does not imply that such embodiment isessential to the subject technology or that such embodiment applies toall configurations of the subject technology. A disclosure relating toan embodiment may apply to all embodiments, or one or more embodiments.An embodiment may provide one or more examples of the disclosure. Aphrase such an “embodiment” may refer to one or more embodiments andvice versa. A phrase such as a “configuration” does not imply that suchconfiguration is essential to the subject technology or that suchconfiguration applies to all configurations of the subject technology. Adisclosure relating to a configuration may apply to all configurations,or one or more configurations. A configuration may provide one or moreexamples of the disclosure. A phrase such as a “configuration” may referto one or more configurations and vice versa.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any embodiment described herein as“exemplary” or as an “example” is not necessarily to be construed aspreferred or advantageous over other embodiments. Furthermore, to theextent that the term “include,” “have,” or the like is used in thedescription or the claims, such term is intended to be inclusive in amanner similar to the term “comprise” as “comprise” is interpreted whenemployed as a transitional word in a claim.

All structural and functional equivalents to the elements of the variousaspects described throughout this disclosure that are known or latercome to be known to those of ordinary skill in the art are expresslyincorporated herein by reference and are intended to be encompassed bythe claims. Moreover, nothing disclosed herein is intended to bededicated to the public regardless of whether such disclosure isexplicitly recited in the claims. No claim element is to be construedunder the provisions of 35 U.S.C. § 112, sixth paragraph, unless theelement is expressly recited using the phrase “means for” or, in thecase of a method claim, the element is recited using the phrase “stepfor.”

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but are to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. Pronouns in themasculine (e.g., his) include the feminine and neuter gender (e.g., herand its) and vice versa. Headings and subheadings, if any, are used forconvenience only and do not limit the subject disclosure.

What is claimed is:
 1. A system for dose dispensing, the systemcomprising: one or more processors; and a memory including instructionsthat, when executed by the one or more processors, cause the one or moreprocessors to: secure a first container including a medication in afirst location within an automated dispensing device, the firstcontainer including a first amount of the medication; secure a secondcontainer including the medication in a second location within theautomated dispensing device, the second container including a secondamount of the medication; receive a selection identifying an order forthe medication, the order including at least a maximum amount toadminister; determine that the first amount and the second amount aresufficient to provide the maximum amount; determine that a first wasteamount after administering the maximum amount from the first containeris less than a second waste amount after administering the maximumamount from the second container; and activate the automated dispensingdevice to permit access to the first location.
 2. The system of claim 1,the instructions further causing the one or more processors to log thefirst waste amount as undocumented waste if the first waste amount isnot disposed of at the time the first amount of the medication isremoved from the automated dispensing device.
 3. The system of claim 1,the instructions further causing the one or more processors to determinean amount of time a user to whom the first amount of the medication wasdispensed has to dispose of the first waste amount after the firstamount of the medication is removed from the automated dispensingdevice.
 4. The system of claim 3, wherein the determined amount of timeis based on one or more characteristics of the medication.
 5. The systemof claim 3, wherein the determined amount of time is based on one ormore characteristics of the dosage form of the medication.
 6. The systemof claim 3, wherein the determined amount of time is based on one ormore characteristics of how the medication is to be administered.
 7. Thesystem of claim 3, wherein the determined amount of time is based on oneor more characteristics of the condition of a patient who is to receivethe medication.
 8. The system of claim 1, the instructions furthercausing the one or more processors to initiate a timer associated with auser identifier of a user to whom the first amount of the medication wasdispensed.
 9. The system of claim 8, the instructions further causingthe one or more processors to store an indication that the user disposedof the first waste amount of the medication before the timer reached atimeout threshold.
 10. The system of claim 8, the instructions furthercausing the one or more processors to generate a notification that theuser failed to dispose of the first waste amount before the timerreached a timeout threshold.
 11. The system of claim 10, theinstructions further causing the one or more processors to generate anotification that the user should not be allowed access to any othermedications in the automated dispensing device.
 12. The system of claim10, the instructions further causing the one or more processors togenerate a notification that system wide access privileges for the userare revoked.
 13. The system of claim 8, the instructions further causingthe one or more processors to generate a notification that disposal ofthe first waste amount before the timer reached a timeout threshold wasnot verified by a witness.
 14. The system of claim 8, the instructionsfurther causing the one or more processors to display, on a display ofthe automated dispensing device, a time limit for disposal of the firstwaste amount.
 15. The system of claim 8, the instructions furthercausing the one or more processors to concurrently manage multipletimers associated with the user identifier of the user to whom the firstamount of the medication was dispensed.
 16. The system of claim 1, theinstructions further causing the one or more processors to: determine anactual amount of the first amount of the medication disposed of into awaste device; compare the actual amount of the disposed medication tothe first waste amount; and generate a notification if there is adiscrepancy between the actual amount of the disposed medication and thefirst waste amount.
 17. The system of claim 16, wherein the actualamount of the disposed medication is determined by one of a pill count,a liquid volume measurement and a measured weight of the disposedmedication compared to a per unit weight of the dispensed first amountof the medication.
 18. The system of claim 1, the instructions furthercausing the one or more processors to authenticate an identifier of auser, wherein access to the first location is permitted only after theidentifier of the user is authenticated.
 19. A system for dosedispensing, the system comprising: one or more processors; and a memoryincluding instructions that, when executed by the one or moreprocessors, cause the one or more processors to: secure a firstcontainer including a medication in a first location within an automateddispensing device, the first container including a first amount of themedication; secure a second container including the medication in asecond location within the automated dispensing device, the secondcontainer including a second amount of the medication; receive aselection identifying an order for the medication, the order includingat least a maximum amount to administer; determine that the first amountand the second amount are sufficient to provide the maximum amount;determine that a first waste amount after administering the maximumamount from the first container is the same as a second waste amountafter administering the maximum amount from the second container;determine that the first amount of the medication has a lower configureddispense order than the second amount of the medication; and activatethe automated dispensing device to permit access to the first location.20. The system of claim 19, wherein the dispense order of the first andsecond amounts of the medication are configured by a pharmacy.